Add HTTP/3 early request processing note to Kestrel overview - #37574
Add HTTP/3 early request processing note to Kestrel overview#37574wadepickett with Copilot wants to merge 4 commits into
Conversation
Co-authored-by: wadepickett <10985336+wadepickett@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
The new bullet text slightly misattributes the optimization to the HTTP/3 protocol rather than Kestrel, so it should be reworded for technical accuracy.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
Adds a discoverability note to the Kestrel overview so readers can find the .NET 11 HTTP/3 early request processing improvement without duplicating content from the dedicated HTTP/3 article.
Changes:
- Updates the Kestrel features list to include a .NET 11-qualified link to the HTTP/3 “Early request processing” section.
- Updates
ms.dateto the current date.
File summaries
| File | Description |
|---|---|
| aspnetcore/fundamentals/servers/kestrel.md | Expands the HTTP/3 feature bullet with a .NET 11 note and xref anchor to the HTTP/3 early request processing section; updates metadata date. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
The new deep link targets an anchor that only exists in the HTTP/3 article’s >= aspnetcore-11.0 content, so the link won’t resolve correctly in older doc views (for example, aspnetcore-10.0).
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
There was a problem hiding this comment.
🟡 Changes recommended
The updated bullet doesn’t currently include the PR-described .NET 11-qualified deep link to the “Early request processing” section, and should gate that link by moniker to avoid broken anchors in older views.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
| * **Security hardened:** Kestrel supports HTTPS and is hardened against web server vulnerabilities. | ||
| * **Wide protocol support:** Kestrel supports common web protocols, including: | ||
| * HTTP/1.1, [HTTP/2](xref:fundamentals/servers/kestrel/http2) and [HTTP/3](xref:fundamentals/servers/kestrel/http3) | ||
| * HTTP/1.1, [HTTP/2](xref:fundamentals/servers/kestrel/http2) and [HTTP/3](xref:fundamentals/servers/kestrel/http3). Starting in .NET 11, Kestrel uses early request processing for HTTP/3 to reduce first-request latency. For more information, see [HTTP/3](xref:fundamentals/servers/kestrel/http3). |
|
This got fairly messy for a one line fix while trying to let Copilot handle it. Closing and starting over. |
The .NET 11 HTTP/3 early request processing improvement (Kestrel no longer waits for the control stream and initial SETTINGS frame before processing requests) is documented in the HTTP/3 sub-article but not discoverable from the Kestrel overview landing page.
Per the maintainer's AI triage guidance, this adds a minimal cross-reference on the overview rather than a standalone section that would duplicate the sub-article.
Changes
aspnetcore/fundamentals/servers/kestrel.md.NET 11-qualified link to the sub-article'searly request processingsection.ms.date.Notes
>= aspnetcore-10.0moniker block, so the note is text-qualified with "Starting in .NET 11" to gate the>= aspnetcore-11.0feature without restructuring the list.#early-request-processinganchor matches the## Early request processingheading inhttp3.md.Internal previews
Build report